DI Lines Details

NDC bookings create DI lines.

These lines provide details about the booking, such as price, flight information, confirmation, ticketing time limits, fees, and form of payment. Lines display in sequential order with the oldest entries at the top and the most recent entries at the bottom of the list.

Select a link below to view information about those lines.

Note: Canceled DI lines are available in booking file history.

Airline record locator and NDC identifier

The NDC identifier in DI remarks differentiates NDC booking files from LCC or GDS ones.

Travelport+:  TAS01#REFaa/QUP2X5/AUD/NDC  

CODE DESCRIPTION

DOCI-FREE TEXT-#

Travelport+ only

Document itinerary remark used for all entries

TAS

Identifier

nn#

Fare number (nn)

REFaa

NDC airline reference (REF) followed by the two-character NDC airline code

/text

 

Separator (/) followed by the NDC airline record locator.

/aaa

Separator (/) followed by the three-alpha currency code.

/NDC Separator (/) followed by NDC, which identifies this booking as an NDC booking.

Order ID

When an NDC booking is created by a new booking or an order divide operation, the OID identifies the Order ID for all airlines. NDC deals with Offers (shop/price) and Orders (bookings), so Order ID is recognized by NDC carriers more than booking reference/vendor locator.

Format after TASnn:

OIDcc/xxxxxxxxxx/aaa/NDC
Code Description

Mandatory/

Optional

OID

Identifier for the Order ID

M

cc

Two-character airline code

M

/xxxxxxxxxx/

Denotes the Order ID for the booking

M

aaa

Defines the currency used by the PCC for the booking

M

/NDC

Identifies an NDC booking

M

Example:

#TAS01#OIDQF/QF081BE30BED4/AUD/NDC

Passenger fare and tax breakdown information

Format after TASnn:

P01ADT/168.75/37.81/188.86
CODE DESCRIPTION

Pnn

Passenger identifier (P) followed by the passenger number (nn)

ADT

Indicates a Passenger Type Code of adult

/nn.nn

Separator (/) followed by the base fare (nn.nn)

/nn.nn

Separator (/) followed by the tax (nn.nn)

/nn.nn

Separator (/) followed by the total (nn.nn)

Format after TASnn:

P01ADT/QR20.75/UO6.00/WG11.06
CODE DESCRIPTION

/QR20.75/UO6.00/WG11.06

Separator (/) followed by the two-alpha tax code followed by the tax amount (nn.nn). This entry will repeat for each tax code and amount needed.

Flight details for a segment

Format after TASnn:

S01FLTaannnn/Q/24APR2025/SYDMEL/08000935
CODE DESCRIPTION

Snn

Segment identifier (S) followed by the booking file segment number for the flight (nn)

FLTaannnn

FLT – Flight identifier

aa – carrier code

nnnn – flight number

/aa

Separator (/) followed by the class code

/ddmmmyyyy

Separator (/) followed by the date format (e.g., 17JUN2025)

/aaabbb

Separator (/) followed by the origin and destination codes

/hhmmhhmm

Separator (/) followed by the departure and arrival times

Hold Booking remarks

When an NDC airline supports Hold Bookings, an itinerary remark is added to indicate that the booking was initially completed without payment and that payment must be added within a set time limit to prevent the booking being auto-cancelled by the NDC airline.

Format after TASnn:

RESERVATION CONFIRMED 04APR19 1938Z
CODE DESCRIPTION

RESERVATION CONFIRMED 04APR25 1938Z

Standard text for confirmed reservation

04APR25 indicates the booking date

1938 indicates the booking time (hhmm) in Zulu time

Format after TASnn:

TICKET TIME LIMIT 05APR25 2359Z
CODE DESCRIPTION

TICKET TIME LIMIT

05APR25 2359Z

Standard text for HOLD Booking

05APR25 2359Z indicates the date and time (Zulu) by which the booking must be ticketed.

Transaction total

NDC booking total. Format after TASnn:

TOT566.56
CODE DESCRIPTION

TOT566.56

TOT indicates that this amount is the total amount.

566.56 is the total amount (nn.nn).

Ticket numbers

Ticket numbers as received from the NDC airline. Ticket numbers are per passenger.

Format after TASnn:

TKT/P01/S01-02/08157476215350
CODE DESCRIPTION

TKT

Identifies ticketing information

/P01

Separator (/) followed by P (passenger identifier) and the passenger number

/S

Separator (/) followed by S to indicate segments

nn-nn

or

nn.nn

01-02 indicates a segment range (both segments 1 and 2). To specify segments 1 through 3, enter 01-03.

To indicate specific segments, use a period (e.g., to specify only segments 1 and 3, enter 01.03).

/08157476215350

Separator (/1) followed by the ticket number

If a fee is collected and an EMD is issued, the EMD identifier indicates the transaction. The associated passenger number is included followed by the ticket number.

Format after TASnn:

EMD-S/P01/08157476215350
CODE DESCRIPTION

EMD-S

EMD identifier (EMD) – A or S

/P

Separator (/) followed by

P – Passenger identifier

nn

Passenger number

/aaaaaaaaaaaaaaa

Separator (/) followed by ticket number.

Fees

Fees applied on each traveler in the booking.

Format after TASnn:

P01ADT/FEE6.00/UO1.73
CODE DESCRIPTION

P01ADT

Indicates passenger 1 is an adult.

/FEE6.00/UO1.73

Separator (/) followed by FEE, which indicates the total charge for OB fees associated to the traveler (e.g., credit card, seats, change fee). In this example, the fee is 6.00.

Any amount following the fee indicates the tax associated to the fee.The two-letter tax code is followed by the tax amount.

DI line format for fee and any associated taxes associated to the fee:  FEE<BaseFee>/<TaxCode><TaxAmount>

Form of payment

Format after TASnn:

FOPCC/AXXXXXXXXXXXX1002/566.55/04APR25 1941Z
FOPCA/566.55/04APR25 1941Z
CODE DESCRIPTION

FOP

Form of payment identifier

aa

The two letters following FOP indicate the type of payment.

  • CC indicates credit card.

    • Followed by a separator (/), the two-letter credit card code, and the masked credit card number.

    • Credit card information is followed by a separator (/) and the amount charged

  • CA indicates cash. It is followed by a separator (/) and the payment total (nn.nn).

/DDMMMYY HHMMZ

Separator (/) followed by the ticket issuance date and time in Zulu (Z).

Format after TASnn:

FOPTKT/08157476215350/04APR25 1941Z
CODE DESCRIPTION

FOP

Form of payment identifier

TKT

Indicates that the payment is for a ticket.

/08157476215350

Separator (/) followed by ticket number.

/04APR25 1941Z

Separator (/) followed by the ticket issuance date (DDMMMYY) and time (HHMM) Zulu (Z).

Cancel un-ticketed itinerary

Remarks indicate if the cancel results in a void, refund, or credit on hold.

Format after TASnn:

NDC RES CXL 21JAN 1651Z
CODE DESCRIPTION

NDC RES CXL

Indicates reservation has been canceled

21JAN 1651Z

Indicates the date and time (Zulu) that the itinerary was canceled.

Cancel ticketed itinerary

Remarks indicate if the cancel results in a void, refund, or credit on hold.

Format after TASnn:

NDC RES CXL TKT VOID 21JAN 1651Z
NDC RES CXL TKT RFND 21JAN 1651Z
NDC RES CXL CREDIT ON HOLD 21JAN 1651Z

The text following NDC RES CXL indicates the type of cancel:

  • TKT VOID occurs when the cancellation is within the void window.

  • TKT RFND occurs when cancellation is outside the void window and a refund applies.

  • CREDIT ON HOLD occurs when the user requested that the unused ticket be placed on hold for future use.

Credit on hold details

The flow for a Credit on Hold (COH partially used) itinerary:

Original booking

  • Fare for segment 1: AUD 200.15; fare for segment 2: AUD 582.12; total price of the booking: AUD 782.27

  • Segment 1 was used and the booking was canceled with remaining funds (retained as credits).

  • In the current PNR, the retained credits display the total value of the booking (e.g., AUD 782.27), including the fare of the used segment.

When using the credits against a new booking:

  • New booking example for a new date with a higher cabin type; total fare of new booking is AUD 957.77

  • During reshop, the value of the used segment is added to this new fare.

    E.g., new fare = AUD 957.77 + AUD 200.15 (used) = AUD 1157.92.

  • Since the original fare = AUD 782.27, the differential = 375.65.

  • This is the same as the new fare = AUD 957.77. Original fare excluding used segment = AUD 582.12, so the differential = 375.65.

Itinerary remarks after modify

Remarks indicate that the original itinerary was modified.

NEW/ indicates the newly modified flight segment.

ORIGINAL/ indicates the previous flight segment.

Format after TASnn:

ITINERARY MODIFIED 09NOV24 1938Z
NEW/S01FLTAA1805/Q/25JAN2025/DFWOKC/10401138
ORIGINAL/S01FLTAA1805/Q/25JAN2025/DFWOKC/08400938
CODE DESCRIPTION

ITINERARY MODIFIED

Indicates that the itinerary was modified

09NOV24 1938Z

Date and time that the itinerary was modified (Z indicates Zulu).

When the itinerary is modified after booking file Sync due to an involuntary schedule change, an extra label is added in the header:

Format after TASnn:

ITINERARY MODIFIED INVOL SCHED CHNG 05MAY21 0453Z
NEW/S01FLTAA1805/Q/25JAN2022/DFWOKC/10401138
ORIGINAL/S01FLTAA1805/Q/25JAN2022/DFWOKC/08400938

Refund applied to original form of payment

Remarks indicate if a cancel or an exchange resulted in a refund.

Format after TASnn:

REFUND111.56
CODE DESCRIPTION

REFUND

REFUND as the result of a cancellation or an exchange

111.56

Refund amount (nnn.nn)

Refund/Charge applied to EMD

Remarks indicate if an exchange yield to a refund or charge.

Format after TASnn:

EMD/P01/08122234567666/Refund/GBP/14.90
EMD/P01/08122234567666/ChangeFee/GBP/14.90
CODE DESCRIPTION

EMD

EMD

/P01

Separator (/) followed by P (passenger identifier) and the passenger number.

/08122234567666

Separtor (/) followed by the EMD number

/EMD Type Text

Separtor (/) followed by the EMD type that is returned by carrier, such as Refund, ChangeFee, ReBookingFee.

/GBP

Separator (/) followed by the currency code

/14.90

Separator (/) followed by the amount

Ancillary related EMD issued by carrier

Remarks indicate ancillary type, traveler sequence number, segment sequence number, EMD number with the amount charged against the EMD for the ancillary.

Format after TASnn:

EMD/P01/S02/1234567890/SEAT/USD/25.00
EMD/P02/S02/1234567890/SEAT/USD/35.00
CODE DESCRIPTION

EMD

EMD

/P01

Separator (/) followed by P (passenger identifier) and the passenger number.

/S02

Separator (/) followed by S (segment identifier) and the segment number.

/1234567890

Separator (/) followed by the EMD number.

/SEAT

Separator (/) followed by the ancillary type, such as SEATS.

/USD

Separator (/) followed by the currency code.

/35.00

Separator (/) followed by the amount in nn.nn format.

Modify ticketed itinerary results in an even exchange

Remarks indicate an even exchange.

Format after TASnn:

EVEN EXCHANGE

Ancillaries

Seat

Seats can only be assigned by passenger and by segment (ranges not permitted). Only confirmed seats will be written in the DI lines.

Free seat format after TASnn:

DAS/P01/S01/SEAT/23A
DAS/P01/S02/SEAT/24A

Paid seat format after TASnn:

DAS/P01/S01/SEAT/23A/USD/25.00
DAS/P01/S02/SEAT/23B/USD/28.00

Free and paid seat format after TASnn:

DAS/P01/S01/SEAT/23A
DAS/P01/S02/SEAT/23B/USD/28.00
CODE DESCRIPTION

DAS

Optional Services identifier (DAS)

/P01 

 

Separator (/) followed by P (passenger identifier) and the passenger number.

/S02

Separator (/) followed by S (segment identifier) and the segment number.

/SEAT

 

Separator (/) followed by the optional service item name, such as SEAT.

/23A

Separator (/) followed by the seat number

/USD Separator (/) followed by the currency code

/28.00

Separator (/) followed by the cost

Other Ancillaries

Other ancillaries are stored in Itinerary Remarks and referenced to a passenger segment. The ancillary name displays with the applicable 4-6 letter NDC code.

Format after TASnn:

DAS/P01-03/S01-02/AIRPORT CHECKIN-TSCI/6.00/6
DAS/P01/S01-02/HOLDBAGS-BGPP/10.00/2
DAS/P01.03/S01-02/GOLF CLUBS-BGSPGF/10.00/4
CODE DESCRIPTION

DAS

Optional Services identifier (DAS)

/P01

Separator (/) followed by P (passenger identifier) and the passenger number.

  • 01 indicates only passenger 1.

  • 01-03 indicates passengers 1, 2, and 3.

  • 01.03 indicates only passengers 1 and 3.

/S01-02

Separator (/) followed by S (segment identifier) and the segment number.

  • 01 indicates only segment 1.

  • 01-03 indicates segment 1, 2, and 3.

  • 01.03 indicates only segment 1 and 3.

/AIRPORT CHECKIN-TSCI

Separator (/) followed by the optional service name. The name should be similar to the name Optional Services screen with Optional Service code concatenated.

/6.00

Separator (/) followed by the unit cost (n.nn)

/6

Separator (/) followed by the number of units (total number of units of all passengers)

Reissue of tickets - schedule change - Reason and/or Waiver Code

When a booking has a schedule change resulting in disassociation of the tickets for the passengers in the booking file, the agent must manually reissue the tickets for the passengers in the booking using reason and/or waiver code. This ensures that the passengers do not incur any fees or charges during reissue of the tickets on the flights with the schedule change. This same information is updated in the DI lines for the GDS booking detailing that the tickets generated for the passengers do not use any known FOP but is an even exchange. The reason and/or waiver codes are used for the same.

Format after TASnn:

EVEN EXCHANGE-WAIVER XXXXXXXX REASON YY
CODE DESCRIPTION

EVEN EXCHANGE-

Constant literal - defines that the tickets generated are an even exchange

WAIVER XXXXXXXX

 

Optional

If waiver code is used then this would display within the DI line.

WAIVER – Constant literal

BLANK – Literal space delimiter

XXXXXXXX – Waiver code used by agent (free form text – no length restriction)

BLANK – Literal space delimiter

REASON YY

Reason code is currently mandatory for all implemented carriers.

REASON – Constant literal

BLANK – Literal space delimiter

YY – Reason code used by agent – numeric (possible values 1,2,3,4,5,14)

Fare Type, Account and Corporate Code

When a booking is created or modified for an NDC Order, the Offer used is clearly identified and cross referenced. This creates an audit trail for back office providers, attained by the Fare Type and Account Code/Corporate Deal that was used to generate the offer, to be captured as a new invoice remark once the Order has been created or modified.

Format after TASnn:

PccAAA/FARETYPE/XXXXXXXXXXX/YYYYYY
Code Description

Mandatory/

Optional

P Denotes that this Remark line is for a passenger

M

cc Denotes the passenger number in the booking

M

AAA Denotes the three character Passenger Type Code (PTC)

M

/FARETYPE/

Constant Literal – defines that followup details are the fare type

M

XXXXXXXXXXX

This text is updated based on the different Fare Type returned by the carrier and the prevalent mapping for the same.

Possible values include PUBLICFARE, AIRLINEPRIVATEFARE, etc.

M

/YYYYY

Denotes the account code or corporate code as used by the agent or passenger during booking or modification

O

Examples after TASnn:

P01ADT/FARETYPE/PUBLICFARE
P01ADT/FARETYPE/AIRLINEPRIVATEFARE/FLX50
P01ADT/FARETYPE/AIRLINEPRIVATEFARE

Fare Basis Code

An additional DI line is included when a new itinerary is booked or when an update is made to the existing NDC offer. This DI line provides the fare basis code(s) used for the booking, indicating which fare basis was used for which segments and which passenger.

Format for the DI line for one fare basis, one passenger, one segment booking after TASnn:

FAREBASIS/<FareBasis>//<Segments>/<Passenger>

When using a multi-fare basis code itinerary, the lowest segment number is added in the first line, the next highest is in the next line, etc.

Code Description

Mandatory/

Optional

FAREBASIS

Constant literal – defines that followup details are the fare basis

M

/XXXXXXXXXXX/

Denotes the fare basis code

M

/<Segments>/

Denotes the segment details

Example: /S01.04-05/

"-" represents the continuity and "." represents the continuity break.

M

<Passenger>

Denotes the three-character Passenger Type Code PCC

M

Example of a one fare basis itinerary, if continuity in the segments after TASnn:

FAREBASIS/B1N0C4S1IN//S01.04-05/INF
FAREBASIS/B1N0C4S1IN//S01-02.04-05/INF

Note: "." represents the continuity break and "-" represents the continuity.

Example of an itinerary using more than one fare basis code after TASnn:

FAREBASIS/ESQW1//S01/ADT
FAREBASIS/ESQW1CH//S01/CHD
FAREBASIS/SDQW//S02/ADT
FAREBASIS/SDQWCH//S02/CHD

Involuntary PNR Cancel

This line represents the involuntary booking file/PNR cancel information of an original itinerary.

Format after TASnn:

NDC RES CXL INVOL CXL 05MAY25 1938Z
ORIGINAL/S01FLTAA1805/Q/04MAY2025/DFWOKC/08400938
Code Description

NDC RES CXL INVOL CXL

Standard text for involuntary cancel

DDMMMYY HHMMZ

Itinerary modify Zulu day and time

Segment Type

Original indicates the original flight segment

S{nn}

Segment identifier (S) followed by 1 or 2 numeric (nn) which is from the PNR segment number for this flight

FLTaannnn

Flight Identifier (FLT) followed by 2-character carrier code, then 4-numberic flight number

/aa

Separator (/) followed by the class code

/DDMMMYYYY

Separator (/) followed by the date

/aaaaaa

Separator (/) followed by the origin and destination three-letter airport codes

/hhmmhhmm

Separator (/) followed by the departure and arrival times